home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
QRZ! Ham Radio 4
/
QRZ Ham Radio Callsign Database - Volume 4.iso
/
files
/
packet
/
thenet
/
tn212.exe
/
TN211-4.DOC
< prev
next >
Wrap
Text File
|
1993-08-09
|
6KB
|
107 lines
TN211-3.DOC
NETWORKING OVERVIEW
***********************
There are two TNC-2 based amateur network concepts in use today. These are
the STATIC and the DYNAMIC routing concepts. Each has advantages and
disadvantages. An example of the static routing concept is ROSE, developed
by Tom Moulton, W2VY. With Static routing, a configuration file is prepared
listing all of the nodes with appropriate routes and loaded into each static
node. If available, secondary routing information is also listed in case
primary routes fail.
The advantage of static routing is it does not require system overhead,
due to all routes being preprogrammed. This is considered advantageous as
system overhead adds to circuit loading, thus depriving users a certain amount
of channel capacity. Another advantage of static routing is it forces the
system providers into MANAGING their networks. Here we are assuming this
will lead to efficient network performance. Addition of new nodes into the
system can only happen following coordination and, upon consent of the network
manager.
With dynamic routing, each node has a means of becoming "automatically
aware" of other nodes, and of their relative position in the network. To be
truly "dynamic," it's desirable routing information be kept reasonably current
with updates on new nodes entering the system and the deletion of nodes that
have failed.
TheNet accomplishes this by each node periodically broadcasting its own
existence plus a listing of other nodes heard during broadcasts by neighbor
nodes. This information propagates from node-to-node throughout the network
in a domino-like fashion. Included in the broadcasts is routing information
based on a theoretical concept termed "path quality". This concept says the
path quality between any two nodes is assigned a numerical value as determined
by factors relating to the type of path and it's baud rate. For instance, we
can easily recognize the path quality over a full-duplex wire-link directly
connected between two TNC's at 9600 baud is MUCH better than is an interference
ridden HF channel at 300 baud. Path quality then can be considered a function
of received DATA versus TIME (throughput), with larger amounts equating to
better path quality and lesser amounts to poorer quality.
In a system there may be several alternative routes to any one destination.
As used in TheNet systems, path quality is important since it's the means for
the node to select the best route to a destination node. Figure 1 lists the
recommended path quality values for various types of circuits.
TYPE OF PATH PATH QUALITY RELIABILITY
------------------------------------------------------------------------------
9600 baud RS-232 wire line link (2 TNC's). 255 99%
9600 baud RS-232 satellite link (2 TNC's). 252 98%
9600 baud RS-232 diode matrix (3 TNC's). 248 97%
9600 baud Hidden transmitter-free radio link. 240 94%
1200 baud Hidden transmitter-free radio link. 224 88%
1200 baud Multi-user radio link. 192 75%
1200 baud Multi-user WAN HF radio link. 180 70%
300 baud Multi-user HF radio link. 128 50%
------------------------------------------------------------------------------
FIGURE 1
The path quality approximations above are for "ideal conditions," and are
the values typically assigned by individual NodeOps within the network. The
following example illustrates the algorithm used in selecting routing qualities
to destination nodes.
1200 baud simplex multi-user network
------------------------------------
CASTRO <192> BELVU <192> CORNWL <192> DEAL
192/256 X 192/256 X 192/256 = 108/256
On this system, the route between each neighbor node has a path quality
value of 192. Using the formula: Path Quality divided by 256 times Path
Quality divided by 256 for each of the three hops yields a circuit path quality
value of 108 between CASTRO and DEAL.
9600 baud hidden transmitter-free network
---------------------------------------------------
MILTY <240> ACME <240> JUSTIN <240> DEAL2
240/256 X 240/256 X 240/256 = 211/256
MILTY's routing table would list the destination path to DEAL2 as a "211."
A user requesting a connect to DEAL2 would be routed via the above path unless
a higher path quality route existed.
New nodes in the network broadcast their existence to their neighbors and
are added TO the routing tables. In order to scrub failed nodes FROM the
routing tables, every TheNet node has a "node keep alive" counter. The first
time a neighbor node broadcast is received, the node assigns an initializing
number value to the received node. When a broadcast is missed, the
initializing number is decremented by one (1). Should a series of broadcasts
by that node be missed and the counter decrements to zero, that node's listing
is deleted from the routing table and is no longer included in future node
broadcasts. However if, before reaching zero a broadcast is received, the
initializing counter is reset.
An advantage of TheNet is, once setup, the NodeOp can pretty well trust
the automatic features to take care of networking changes. The node will
require little or no intervention unless a catastrophic failure occurs.
Attention paid to initial node setup will reduce overhead and allow it to
perform as a "good neighbor" within the networking community. Another
advantage TheNet has for some is it broadcasts the NodeOp's callsign
throughout the system. This is a recognition reward for the time and money the
NodeOp has invested.